Constants:

CTools™ now does constants fairly well!.  Yaaaay!  About 95% of them will require no further editing IF you want #defines.  The remaing 5% will be fixed.  Until then, you have to clean these up manually.  What I do is copy them all out to a new file where I can use Find/Replace without messing up something else, fix them all up fast and copy/paste them back.

Here’s an example of output which balked:

Pascal input:
HOMEKEY = chr(1);

CTools™ output:
#define HOMEKEY chr#define 1/***# Expected const identifier ***/

Correction:

Replace All “/***# Expected const identifier ***/” with a space and Find
all the second “#define “ using Command G/H and replace with a space, to get:

#define HOMEKEY chr 1

See...  I only just got it to do constants into defines.  I need to add something to handle parens and such.

If the constant has more than a definition and a meaing, such a a plus or anything more than two words, it will go out of synchronization.  The output can still be editied but not as easily as if the were merely commented out ahead of time.

On a multi-file, use CTools™ “#define” keyword to navigate down the file, to get to where these incorrectly translated contants are.